Network to network interface (nni) for multiple private network service providers

ABSTRACT

An Ethernet exchanger connected to private Ethernet networks of participating carriers to enable the private Ethernet networks to be interconnected at a common point. The Ethernet exchanger not biased to any participating carrier and is configured to receive, translate and transmit frames from one private Ethernet network to another private Ethernet network. The frame translation is performed by the Ethernet exchanger is based on the profiles of the participating carriers. The profiles are created based on information provided by the participating carriers using templates presented by an online web portal.

RELATED APPLICATIONS

This application claims the benefit of and priority to all three: 1)U.S. Provisional Application titled “ETHERNET EXCHANGE” filed on Dec.10, 2009 having application Ser. No. 61/285,371 and is incorporatedherein by reference in its entirety; 2) U.S. Provisional Applicationtitled “PRIVATE NETWORK CONNECTIVITY PLATFORM” filed on Sep. 4, 2009having application Ser. No. 61/239,997 and is incorporated herein byreference in its entirety; and 3) U.S. Provisional Application titled“ETHERNET EXCHANGE” filed on Apr. 12, 2010 having application Ser. No.61/323,066 and is incorporated herein by reference in its entirety.

NOTICE OF COPYRIGHT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the software engineand its modules, as it appears in the Patent and Trademark Office Patentfile or records, but otherwise reserves all copyright rights whatsoever.

FIELD OF THE INVENTION

Embodiments of the invention generally relate to network connectivity ina many-to-many connection environment. More particularly, an aspect ofan embodiment of the invention relates to a standardized technique tointerconnect private Ethernet networks of service providers usingnetwork-to-network interface (NNI).

BACKGROUND OF THE INVENTION

One of the challenges that many network carriers face is how to maketheir services available to their customers at competitive costs. Thecustomers may be located anywhere, and it can be cost prohibitive foreach carrier to install their own end-to-end wiring to service thesecustomers. Many carriers already have existing high speed networks(e.g., fiber) in many metropolitan areas. As such, it is possible forone carrier to connect to an existing network of another carrier. Thistype of connection is referred to as Direct Network to NetworkInterconnection (D-NNI). Typically, the D-NNI approach is very complexand time consuming. It takes a lot of time for the two carriers tonegotiate an agreement and for their engineering teams to come up with asolution. The process is repeated whenever a connection with anothercarrier is required, making it very inefficient and costly.

SUMMARY OF THE INVENTION

For some embodiments, a carrier-neutral Ethernet exchanger is configuredfor the participating carriers to connect to each other's Ethernetnetworks, with a standard network-to-network interface (NNI) and with aprocess that reuses already entered or known data preventing the processfrom having to be done from scratch each time repeatedly. Aconfiguration module uses templates from an online web portal to solicitinformation from the participating carrier and then automaticallyextracts that information into a relational database for the informationto be reused. Each time a new template is presented to the participatingcarrier the information now stored in the relational database is used topre-populate known information in a new template presented to theparticipating carrier. This allows for a faster building of the NNIprocess for each participating carrier in a one-to-many solution basedon usage of standards and usage of known information. The online webportal is configured to standardize the NNI connections via having codedroutines for: a) for service connectivity and fabric provisioningbetween carriers connected to ports of the Ethernet exchanger; b)service VLAN ID translation between the solicited VLAN IDs of thenetworks creating a within multiple network environments; c) serviceVLAN frame translation between the solicited VLAN frame type used ineach network being provisioned; d) service MTU adaptation between thesolicited MTU allowed in each network being provisioned; and e) serviceVLAN TPID translation the solicited VLAN TPID assigned in each networkbeing provisioned; and any Quality of Service (QoS) parameters used ineach network being provisioned.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings refer to embodiments of the invention in which:

FIG. 1A is a block diagram that illustrates a high-level view of a datacenter equipped with an Ethernet exchanger, in accordance with someexample embodiments; and

FIG. 1B is a block diagram that illustrates an example of an Ethernetexchanger, in accordance with some embodiments; and

FIG. 1C is a block diagram that illustrates examples of variousinterconnectivity options available to the carriers, in accordance withsome Embodiments; and

FIG. 2 is a diagram that illustrates one example of the optionsavailable to the carriers in a web portal, in accordance with someembodiments; and

FIG. 3A is a block diagram that illustrates an example of Ethernet frametranslation, in accordance with some embodiments; and

FIG. 3B is a block diagram that illustrates another example of Ethernetframe translation with multiple connections, in accordance with someembodiments; and

FIG. 3C is a block diagram that illustrates translation of quality ofservice variable, in accordance with some embodiments; and

FIG. 3D is a table that illustrates an example of bandwidth translation,in accordance with some embodiments; and

FIG. 3E is a table that illustrates an example of Quality of Service(QoS) traverse, in accordance with some embodiments; and

FIGS. 4A-4B are tables that illustrates examples of Class of Service(CoS) mapping, in accordance with some embodiments; and

FIG. 4C illustrates an example of frame size adaptation as configured inan Ethernet exchanger, in accordance with some embodiments; and

FIG. 5 is a block diagram that illustrates an example of monitoring andtroubling shooting tools that may be available to the carriers, inaccordance with some embodiments; and

FIG. 6 is a block diagram that illustrates an example of a marketplace,in accordance with some embodiments; and

FIG. 7A is an example flow diagram that illustrates a process ofproviding interconnectivity services to the carriers, in accordance withsome embodiments; and

FIG. 7B is an example flow diagram that illustrates a process of reusingexisting carrier's information to establish multiple virtual circuits,in accordance with some embodiments; and

FIG. 7C is an example flow diagram that illustrates a process offacilitating partnership among the carriers, in accordance with someembodiments; and

FIG. 8 illustrates an example diagram of a representation of a machinein the example form of a computer system that may be used, in accordancewith some example embodiments; and

FIG. 9 illustrates an overall example diagram of a representation of amarketplace that includes a web portal and an ExternalNetwork-to-Network Interface (E-NNI), in accordance with some exampleembodiments; and

FIG. 10 illustrates an example screen of a web portal, in accordancewith some example embodiments; and

FIG. 11 is an example flow diagram that illustrates a process ofenabling a carrier to utilize services offered by the marketplace, inaccordance with some embodiments; and

FIG. 12 is an example flow diagram that illustrates a process oftranslating and mapping frames for the private Ethernet networks, inaccordance with some embodiments.

While the invention is subject to various modifications and alternativeforms, specific embodiments thereof have been shown by way of example inthe drawings and will herein be described in detail. The inventionshould be understood to not be limited to the particular formsdisclosed, but on the contrary, the intention is to cover allmodifications, equivalents, and alternatives falling within the spiritand scope of the invention.

DETAILED DISCUSSION

According to some embodiments, an Ethernet exchanger is connected to twoor more private Ethernet networks of participating carriers to enablethe two or more private Ethernet networks to be interconnected at acommon point. The two or more private Ethernet networks including afirst private Ethernet network associated with a first Ethernet frametype and a second private Ethernet network associated with a secondEthernet frame type. Frames from the first private Ethernet network arereceived, translated and transmitted by the Ethernet exchanger to thesecond private Ethernet network. Frame translation is performed by theEthernet exchanger based on a first profile associated with the firstprivate Ethernet network and a second profile associated with the secondprivate Ethernet network. The first profile and the second profile arestored in a relational database associated with the Ethernet exchanger.The first profile and the second profile established based oninformation received from a first participating carrier associated withthe first Ethernet network and from a second participating carrierassociated with the second Ethernet network. An online web portal hostedon a server and cooperating with the Ethernet exchanger is used topresent templates to the first and second participating carriers tosolicit information and to enable the information to be stored in therelational database.

In the following description, numerous specific details are set forth,such as examples of specific data signals, named components,connections, amount of private carriers connected to the switch fabric,etc., in order to provide a thorough understanding of the presentinvention. It will be apparent, however, to one of ordinary skill in theart that the present invention may be practiced without these specificdetails. In other instances, well known components or methods have notbeen described in detail but rather in a block diagram in order to avoidunnecessarily obscuring the present invention. Further specific numericreferences such as first private carrier, may be made. However, thespecific numeric reference should not be interpreted as a literalsequential order but rather interpreted that the first private carrieris different than a second private carrier. Thus, the specific detailsset forth are merely exemplary. The specific details may be varied fromand still be contemplated to be within the spirit and scope of thepresent invention. The term “coupled” is defined as meaning connectedeither directly to the component or indirectly to the component throughanother component.

Overview

An Ethernet exchanger is connected to private Ethernet networks ofparticipating carriers to enable the private Ethernet networks to beinterconnected at a common point. The Ethernet exchanger not biased toany participating carrier and is configured to receive, translate andtransmit frames from one private Ethernet network to another privateEthernet network using layer 2 network-to-network interface (NNI). Theframe translation performed by the Ethernet exchanger is based networkinformation provided by the participating carriers. Profiles of theparticipating carriers are created and stored in a relational database.Network information of the private Ethernet networks is also stored inthe relational database. The information from the participating carriersis collected using templates presented by an online web portal.

For some embodiments, a private network exchange is a multiple portswitch fabric, with one or more Ethernet exchangers for two or moreEthernet carriers, integrated with the web portal. The Ethernetexchanger is a system that is designed to address growing demand forEthernet services by enabling carriers to interconnect and to expandtheir services globally. The Ethernet exchanger may be part of anoverall physical Ethernet switch fabric which may include one or moreEthernet exchangers to support single connections as well as redundantconnections.

The Ethernet exchanger is configured to be used by the carriers as acommon point for External network-to-network interconnection (E-NNI).One implementation of the E-NNI may be an Equinix Carrier EthernetExchange™ provided by Equinix, Inc. headquartered in Foster City, Calif.The Ethernet exchanger streamlines and simplifies the process ofpartnering the carriers in a transparent and neutral manner. One exampleapplication of an Ethernet exchanger is a co-location andinterconnecting data center where many carriers already have theirpresence. This allows the participating carriers to have a wide range ofinterconnectivity options in the same facility. The Ethernet exchangerincludes ports for two or more carriers to connect their networkwirings. This enables a carrier to have options to create many-to-manyinterconnections with only one-time hook up to the switch fabric,one-time creation of a customer account with the switch fabric, andone-time providing description of its network characteristics using aweb portal associated with the switch fabric. The customer account mayinclude the user profile information. The Ethernet exchanger enables theusage of already entered or known information thus simplifying theinterconnecting process by avoiding the needs to repeatedly requiringthe carriers to enter their information for every connection.

FIG. 1A is a block diagram that illustrates a high-level view of a datacenter equipped with an Ethernet exchanger, in accordance with someexample embodiments. Ethernet exchanger 100 provides a neutralconnectivity platform to allow carriers to interconnect their networks(also referred to as carrier Ethernet networks or “CEN”s). The Ethernetexchanger 100 is neutral because it is not biased to any carriers andonly provides the interconnectivity service after the carriers becomepartners. The Ethernet exchanger 100 may be deployed in locations wheremany carriers already have their equipments such as, for example, datacenter 101. Each carrier may only need to have one connection to theEthernet exchanger. In the current example, each of the carriers A-F hasone connection to the Ethernet exchanger 100.

By being connected to the Ethernet exchanger 100, a carrier can purchaseservices and reach out to many end users in many different geographicalareas without incurring the same expenses typically associated withhaving multiple D-NNIs. For example, the carrier A can expand itsservices using the carrier D's Ethernet network. By connecting to theEthernet exchanger 100, a carrier may be able to generate additionalrevenue by offering to sell its network services to the other carriers.For example, the carrier D can offer the opportunity to use the carrierD's network to the other carriers.

The Ethernet Exchanger standardizes the network-to-network connectionprocess. It provides the ability to distribute and supportmulti-regional Ethernet connections on one central platform between amany-to-many private network to private network connection. The EthernetExchanger provides a network interoperability and tracking platform thatfacilitates interconnection and peering via an Ethernet centralswitching fabric. The Ethernet exchanger employs a process that reusesalready entered or known data preventing the process from having to bedone from scratch each time repeatedly. As will be described, theEthernet exchanger employs coded routines that allow for a fasterbuilding of the network-to-network interface process for each carrier ina one-to-many solution.

FIG. 1B is a block diagram that illustrates an example of an Ethernetexchanger, in accordance with some embodiments. The Ethernet exchanger100 may include Gigabit Ethernet (Gig-E) ports and 10 Gig-E ports suchas, for example, ports 108, 113, 118 and 123. In one example, theEthernet exchanger 100 may be implemented using routers and switchessuch as a 12-slot Alcatel-Lucent 7450 ESS-12 and one or moreAlcatel-Lucent 7750 Service Routers (SR) of Alcatel-Lucent headquarteredin Paris, France. Each of the ports (also referred to as a physicalconnection) of the Ethernet exchanger 100 may support thousands ofvirtual circuits (also referred to logical connections).

The Ethernet exchanger 100 may be configured to include a configurationmodule 102, a provisioning module 103, and a monitoring module 104.These modules may be implemented using software scripted routines,hardware logic and any combination of both. The provisioning module 103may provision virtual circuits. The configuration module 102 may map andtranslate Ethernet services among the carriers.

The Ethernet exchanger 100 may offer application programming interfaces(APIs) to exchange information with other applications such as, forexample, the web portal used by the participating carriers. In thefollowing discussions, the phrases “participating carriers” “qualifiedcarriers” or “carriers” refer to the carriers who have agreements with aprovider of the Ethernet exchange services such as, for example,Equinix, Inc.

The Ethernet exchanger 100 may also be configured to include a monitormodule 104 which may be implemented using software scripted routines,hardware logic and any combination of both. The monitor module 104 maymonitor the status of the virtual circuits and provide statusinformation to the carriers. As mentioned above, the communication withthe carriers may be via the web portal. Some examples of networkmanagement software used by the monitoring module 102 may includeoperation support systems (OSS) and simple network management protocol(SNMP). OSS and SNMP are network management protocols used to managecommunications networks. The monitor module 104 may be configured to useAPIs to exchange information with network management software used bythe carriers.

The Ethernet exchanger 100 may support multiple E-NNIs. Each of theE-NNIs is coupled to a port. For example, each of the ports 108, 113,118 and 123 is coupled to each of the E-NNI 106, E-NNI 111, E-NNI 116,and E-NNI 121, respectively. In the example illustrated in FIG. 1B, theEthernet services of carrier A and carrier C are mapped and translatedacross virtual circuit 150. This allows Ethernet traffic to flow betweennetwork 105 and network 110. Likewise, the Ethernet services of carrierB and carrier C are mapped and translated across virtual circuit 155.This allows Ethernet frames to be exchanged between network 115 andnetwork 110.

The Ethernet exchanger 100 is configured to support point-to-pointconnections as well as multipoint connections. In a point-to-pointconnection, the Ethernet exchanger 100 establishes a virtual circuitthat connects networks from two carriers. In a multipoint connection,the Ethernet exchanger 100 establishes virtual circuits that connectnetworks from many carriers. For example, the virtual circuit 150 ispart of a point-to-point connection. The virtual circuits 155, 160, 165and 170 are parts of multipoint connections. The Ethernet exchanger 100may map and translate Ethernet services between and among the manyEthernet networks connected by the virtual circuits.

FIG. 1C is a block diagram that illustrates examples of variousinterconnectivity options available to the carriers, in accordance withsome embodiments. The example illustrates two Ethernet switch fabrics190 and 195. The Ethernet switch fabric 190 may be located in onemetropolitan area while the Ethernet switch fabric 195 may be located inanother metropolitan area. Both are communicatively coupled via, forexample, high-speed connection 198. The Ethernet switch fabric 190includes three Ethernet exchangers 191, 192 and 193. An example ofredundant connections is illustrated with the carrier A havingconnections to all three Ethernet exchangers 191, 192 and 193.Similarly, the carrier has redundant connections to the Ethernetexchangers 192 and 193. An example of single connection is illustratedwith the carrier B and the carrier D, having a connection to theEthernet exchanger 192 and 194 respectively.

FIG. 1C also illustrates one advantage of a carrier using an Ethernetexchanger to expand its services in distant geographical areas. TheEthernet switch fabric 190 may be located in a metropolitan area of onecontinent (e.g., North America). The Ethernet switch fabric 195 may belocated in a metropolitan area of another continent (e.g., Europe). Byparticipating in the Ethernet switch fabric platform, the carrier A maybe able to offer Ethernet services to clients/end users located in thecontinent where the carrier D has its presence.

Web Portal

For some example embodiments, the web portal may be configured topresent a questionnaire in the form of templates to solicit informationfrom the carriers. The templates are web-based and may be presented as aweb page or part of a web page. The templates solicit carrierinformation and direct that solicited information into fields of thedatabase. For example, there may be a network services descriptiontemplate, a user profile template, a qualification template, a litbuilding template, etc. The web portal cooperates with the physicalswitch fabric of the Ethernet exchanger 100 to provide the carriers astandardized interconnecting process. The web portal may be a web sitethat offers many services to the carriers including, for example, buy,sell, order, emails, register, manage accounts, etc.

FIG. 2 is a diagram that illustrates one example of the optionsavailable to the carriers in a web portal, in accordance with someembodiments. In this example, web portal 200 may be communicativelycoupled to Internet network 280. The web portal 200 may be associatedwith a computer system that may be coupled to a server system 285 and adatabase system 290. The server system 285 and the database system 290are coupled to the Internet 280 and may be combined into one system, orthey may be separate systems. The database system 290 and the databasesystem 190 (illustrated in FIG. 1B) may be one or separate systems. Theweb portal 200 may run as a web-based application on the server system285. The database system 290 may be configured to store information usedby the web portal 200 or information collected by the web portal 200.

The carriers may use computer systems to access the web portal 200 tocommunicate with one another and to interact with the underlyingEthernet switch fabric such as, for example, switch fabric 190(illustrated in FIG. 1C). For example, the carriers A-D may use clientcomputer systems 281-284 respectively to connect to the web portal 200via the Internet 280. The web portal 200 may include a register optionto allow a carrier to register and become a participant. For example, acarrier (or carrier representative, user, etc.) may use button 265 toregister and to provide information about its networks and services. Thecarrier may need to provide the information via a series of one or moretemplates.

Information provided with the templates may be used for service mappingand provisioning as well as any specific extensible markup language(XML) API translations for web services consumption. XML APIs are APIsthat are coded using XML. The web portal includes codes that arescripted to automate interaction with the underlying switch fabric,service mapping and/or any logical translation based on XML API and webinterface. Each template may be presented by the web portal 200 as a webpage or a pop-up window. The information solicited from the carriers mayinclude information about their networks such as, for example:

Footprint and Lit building list

Service metro area

Building connection bandwidth

Ethernet service type and topology

Supporting Maximum Transmission Unit (MTU) size

Supporting VLAN frame type with tag protocol identifier (TPID)

Network protocol information

Ethernet operation and management (OAM) capability

Contact and Escalation information

For some embodiments, the lit building information may be entereddirectly using the web portal 200. For example, this may be via a litbuilding template. Alternatively, the lit building information may besubmitted and processed as a batch operation. This batch processing maymake it easier for those carriers that have many lit buildings or thosecarriers that have lit building information stored in formats that arenot easily extracted. For some embodiments, the batch processing isperformed using an API associated with the web portal 200.

Many of the fields in the template may correspond to fields of asearchable relational database such as, for example, database 290. Thetemplates may be standardized so that they can be used for all carriers.This is advantageous because there is no need to have different set ofquestions for different carriers as is typically used in the D-NNIs. Inaddition, a carrier may only need to provide the information about itsnetwork once regardless of how many other networks that the carrier maybe interconnected with. Information associated with a carrier may begrouped together as a carrier profile. Each carrier profile may beunique. In addition to storing the carrier profiles, the database 290may also be configured to store other information that may be used bythe web portal 200.

The Ethernet exchanger 100 is configured as a transparent aggregationtranslator between the private Ethernet networks of the carriers. Thetemplates may include a carrier qualification template to allow acarrier to qualify, carrier profile template to allow the carrier tolist user account information, service template to allow the carrier todescribe services offered as well as network capabilities andcharacteristics, etc. Two or more of these templates may be combineddepending on the implementation.

The web portal 200 may be configured to present the templates to a useror representative of the carrier on a client machine to allow the userto create a user profile for its carrier and associated Ethernetnetwork. The user profile may include services offered by the carrier.The configuration module of the Ethernet exchanger 100 may be configuredto extract and store this information in the database. The informationfrom all of the users is aggregated to provide complete and relevantinformation in response to a search query generated by other users usingthe online web portal 200. The database may be associated withintelligent routines to discover the queried information and present theaggregated information to the user that is relevant to the query of theuser. The information may include a list of a carrier's Ethernetbuildings by capacity, price, service level, etc. The information mayalso include lit building list. The templates enable the collection, theextraction, and the storing of the information into the relationaldatabase. The database is configured to store, aggregate and makes theaggregated information searchable and publishable.

The web portal 200 provides a medium that allows a carrier to interact,showcase, and sell its services to other carriers. It allows a carrierto specify information or services that it wants to offer to othercarriers and to learn about other carriers' services. This enables thecarriers to qualify each other as partners and to form relationshipswith one another. For example, a carrier may use the button 250 todescribe services that it is willing to offer to potential partners.Similarly, a carrier may use button 255 to specify services that it issearching for.

For some embodiments, the information about the services being searchedfor may be presented in the form of a request for quote (RFQ). Forexample, the carrier A may use the web portal 200 to search, view andidentify services offered by the carrier D. A representative of thecarrier A may use the button 255 to generate an RFQ and cause the RFQ tobe sent to the carrier D. When a representative of the carrier D issigned on to the web portal, an RFQ notification is displayed. For someembodiments, the account information or the profile information storedin the relational database may be used to populate fields of the RFQ.

Negotiations between the carrier A and the carrier D may then takeplace. For some embodiments, the carriers may negotiate amongthemselves, and then use the web portal 200 to enter the details oftheir agreements. When there is an agreement between the carrier A andthe carrier D, the carrier A may use the button 260 to request theunderlying switch fabric and Ethernet exchanger to provision theservices. It may be noted that the provisioning request may be initiatedby either carrier A or carrier D.

For some embodiments, each carrier may use the web portal 200 toconfigure and assign representatives to different roles (see FIG. 9 forexamples of roles). One representative may be assigned an administratorrole and serve as an administrator. The administrator may then assignother representatives from the carrier to other roles such as, forexample, sales, engineering, product support, technical support, etc.(illustrated as representatives 286, 287 and 288). Each role may beassociated with a different level of access and/or a different level ofcapabilities. For example, only a sale representative may review theagreements of that carrier, and only a technical support representativemay be able to access the network management information.

Provisioning, Mapping and Translation

The Ethernet exchanger 100 is configured to perform interconnectionservice that aggregates and translates private Ethernet services fromthe many participating carriers. It provides a many-to-many Layer 2Network-to-Network Interface (NNI). Carrier information from all of theEthernet networks connected to the Ethernet exchanger is aggregated andstored in the database.

For some embodiments, the configuration module 102 (as illustrated inFIG. 1A) is configured to act as an agent to convert back and forthprotocols, bandwidth requirements, etc. between the variousparticipating carriers. The Ethernet exchanger 100 is also configured touse APIs to work with a multitude of proprietary systems APIs. Theconfiguration module 102 may include logic and/or software routines todo the handshaking, mapping, and conversion between the differentEthernet protocols independent of the type of Ethernet protocol ornetwork configuration parameters used in either Ethernet network.Following are some examples of the operations that may be performed bythe configuration module 102:

Service VLAN ID translation within multiple network environments

Service VLAN frame translation within multiple network environments

Service MTU adaptation within multiple network environments

Service VLAN TPID translation within multiple network environments

Bandwidth protection within E-NNI Fabric

QoS traverse within E-NNI Fabric

FIG. 3A is a block diagram that illustrates an example of Ethernet frametranslation, in accordance with some embodiments. The Ethernet exchanger100 is configured to translate frames received from one network intoframes that are to be transmitted to another network independent of theproprietary protocol used in either network. In FIG. 3A, frame 310 istransmitted from a first network and includes a protocol data unit (PDU)308 and a VLAN tag. The VLAN tag includes a TPID value of 0x8100 and aVLAN ID of 100. The TPID value of 0x8100 is configured by the carrierassociated with the first network. Each of the ports of the Ethernetexchanger 100 is associated with a TPID value that matches with the TPIDof the carrier that is associated with that port.

For some embodiments, the Ethernet exchanger 100 keeps the value of thePDU 308 intact throughout the translation process. When the frame 301 isreceived, the TPID portion of the frame 301 is stripped and aMultiprotocol Label Switching (MPLS) label 307 is added. This isillustrated as frame 302. The positions of the MPLS data 307 and the PDU308 in the frame 302 are then switched, as illustrated in frame 303. TheEthernet exchanger 100 then forward the frame 303 by making switchingdecisions based on the MPLS label 307. The frame 303 is then transmittedacross a virtual circuit to a destination port where the Ethernetexchanger 100 replaces the MPLS label 307 with the TPID associated withthe destination port. As illustrated with frame 304, the TPID value hasbeen translated to 0x88a8 and the VLAN ID has been translated to 200.The TPID value of 0x88a8 is configured by a carrier associated with asecond network. The translated frame is then transmitted from theEthernet exchanger 100 to the second network as frame 305. FIG. 3A alsoillustrates the translation of the VLAN ID. As illustrated, the incomingframe 301 has a VLAN ID=100 corresponding to one Ethernet network. Asthat frame is translated by the Ethernet exchanger 100, its VLAN ID isupdated from 100 to 200 to correspond to the Ethernet network that theframe 305 is transmitted to.

FIG. 3B is a block diagram that illustrates another example of Ethernetframe translation with multiple connections, in accordance with someembodiments. In this example, the Ethernet exchanger 100 translatesframes from three different carriers via E-NNI 310, 320 and 330. Frames309 and 319 are associated with a similar Ethernet type 802.1q, whereasframe 329 is associated with Ethernet type 802.1ad. Similar to theexample illustrated in FIG. 3A, as these frames (shown as frames 350,355 and 360) are received at their respective receiving ports, the frametype and frame ID portion is removed and replaced by MPLS label (or MPLSframe). Their PDU portions remain the same (or ignored and nottranslated). They are then sent across the appropriate virtual circuits.The translation is completed when the MPLS labels are replaced by theframe information associated with the port at the receiving end.

FIG. 3C is a block diagram that illustrates translation of quality ofservice variable, in accordance with some embodiments. In order toprovide consistent quality of service (QoS) across multiple networks bydifferent carriers, the Ethernet exchanger 100 needs to be able totranslate a QoS variable from one carrier to a QoS variable from anothercarrier. For some embodiments, a frame from a carrier may be viewed ashaving three frame components: a service frame, a carrier frame, and aQoS frame. Note the three arrows identified as “preserve”, “translate”and “create a profile” corresponding to each component in the ingressside. On the egress side, the three arrows are identified as “preserve”,“translate” and “translate from the profile” to convey which of thethree components may be modified. The Ethernet exchanger 100 maytranslate the information from the frame 370 into a service frame 390, acarrier frame 391 and a QoS frame 392. The service frame 390 may includethe end user data. The carrier frame 391 may include information aboutthe frame type, VLAN ID and TPID as translated by the Ethernet exchanger100. The QoS frame 392 may include service variable as translated by theEthernet exchanger 100 from a QoS used in the first network to a QoSused in the second network.

It may be noted that the frame portion 372 of the frame 370 is similarto the frame portion 382 of the frame 380. However, the frame portion374 of the frame 370 is translated into the frame portion 384 of theframe 380. This reflects the translation of the QoS between the twonetworks. For some example embodiments, each carrier is required toenter QoS information about their networks using the web portal. Whentwo carriers enter into an agreement, each of the carriers may need touse the web portal to indicate to the Ethernet exchanger 100 which ofthe QoS to use.

FIG. 3D is a table that illustrates an example of bandwidth translation,in accordance with some embodiments. Table 394 includes row heading 395and column heading 396. The content of the table 394 is highlighted inbold. The row heading 395 includes bandwidth information for a serviceoperator (a carrier that is using the network services of anothercarrier). The column heading 396 includes bandwidth information for aservice provider (a carrier that offers services to another carrier).CIR is short for committed information rate, and it represents theaverage bandwidth for a virtual circuit guaranteed under normalconditions, where that the bandwidth should not fall below the committedrate at any time. PIR is short for peak information rate, and itrepresents a highest supported burst rate. The different cells insidethe bold area of FIG. 3D represents the suggested translation of thebandwidth from the operator's network to the service provider's network.For example, if the bandwidth on the operator's network is CIR and thebandwidth on the service provider's network is “Aggregate, Per Q CIR”,then the bandwidth given to the operator on the service provider'snetwork is “Aggregate bandwidth to CIR”. For some embodiments, theservice operator may need to match or adapt to the service provider'smethod to guarantee the service bandwidth. FIG. 3E is similar to FIG. 3Dbut instead illustrates an example of Quality of Service (QoS) traversebetween a service operator (SO) and a service provider (SP), inaccordance with some embodiments.

FIGS. 4A-4B includes tables that illustrate examples of Class of Service(CoS) mapping, in accordance with some embodiments. Table 405 and 410shows the different classes in the row headings and the number ofclasses in the column headings. The traffic direction in both tables 405and 410 illustrates the direction from ingress to egress of a switch,such as the Ethernet exchanger 100. Referring to the table 405, when thenetwork of the incoming traffic supports six CoS types and the networkof the outgoing traffic also supports six CoS types, then there is aone-to-one mapping, as shown in the first column under the “6 CoS”heading. At the other extreme, when the network of the incoming trafficsupports six CoS types and the network of the outgoing traffic onlysupports one CoS type, then all the six CoS classes of the incomingtraffic is mapped to the one CoS supported by the network of theoutgoing traffic, as shown in the last column under the “1 CoS” heading.Similarly, when the network of the outgoing traffic only supports twoCoS types, then the six CoS classes of the incoming traffic is mapped tothe two CoS supported by the network of the outgoing traffic. In thisexample, the incoming CoS 5 and 6 are mapped to CoS 2 and the incomingCoS 1-4 are mapped to CoS 1 supported by the network of the outgoingtraffic, as shown in the column under the “2 CoS” heading. Table 410 ofFIG. 4B illustrates a reverse example of the example illustrated intable 405 of FIG. 4A. In this example, the network of the incomingtraffic may support anywhere from one to six CoS, and the network of theoutgoing traffic may support six CoS types. As can be seen, the mappingmay result in modifying the CoS of the incoming traffic to various CoSsupported by the network of the outgoing traffic.

FIG. 4C is a diagram that illustrates an example of frame sizeadaptation as configured in an Ethernet exchanger, in accordance withsome embodiments. Diagram 450 illustrates that each carrier's networkmay have a different MTU. The MTU may be set by the carrier's networkadministrator, and it represents a largest frame (or packet) size inbytes that a carrier's network can transmit. For some embodiments, whenthe Ethernet exchanger 100 transmits a frame originating from onecarrier network to another carrier network, the frame size may need tobe adjusted. A frame from one carrier network that is larger than theMTU of another carrier may be divided into smaller frames. Asillustrated in FIG. 4A, since the MTU of the carrier A is 9000 bytes,and the MTU of the carrier B is 1526 bytes, the service A can only beable to support up to 1522 bytes (4 bytes from the 1526 bytes is usedfor overhead). Similarly, since the MTU of the carrier C is 4000 bytes,and the MTU of the carrier D is 2000 bytes, the service B can only beable to support up to 1996 bytes (4 bytes from the 2000 bytes is usedfor overhead).

Monitoring and Trouble Shooting

FIG. 5 is a block diagram that illustrates an example of monitoring andtroubling shooting tools that may be available to the carriers, inaccordance with some embodiments. The E-NNI switch fabric 500 and itsEthernet exchangers including, for example, Ethernet exchanger 100, mayinclude scripted codes and/or hardware logic to monitor and report anypotential issues that may affect the transmission of frames across thevirtual circuits. For example, this may include Ethernet Operation andMaintenance (OAM) module 515 and ticketing module 520.

At the web portal level, the carriers may be able to access the monitoroption 505 and the trouble shooting option 510 to interact with theEthernet OAM module 515 and the ticketing module 520. The carriers mayalso be able to receive monitoring and troubleshooting reports 540. Themonitor option may be used by members of the carrier's network operationcenter (NOC) 535 to submit tickets, test status, view link statistics,etc. For some embodiments, APIs may be available to allow the carriers'applications 530 to view monitoring and troubleshooting information andto perform other related network management operations. It may be notedthat the APIs described herein may enable a standard method ofcommunicating and exchanging information of the carriers and informationstored in the database associated with the web portal and the switchfabric.

For some embodiments, a carrier may be able to perform network testingthat encompass its network as well as the virtual circuits that thecarrier is associated with. For some embodiments, the Ethernet exchanger100 may prevent a carrier's test from reaching beyond the virtualcircuit and into another carrier's network. However, when anauthorization is provided, the Ethernet exchanger is configured toprovide monitoring, troubleshooting and ticketing information as relatedto both the virtual circuit provisioned between the first Ethernetnetwork and the second Ethernet network as well as the first Ethernetnetwork and the second Ethernet network themselves.

For some embodiments, the Ethernet exchanger 100 is configured to allowtesting to identify issues are relating to loss of connectivity,performance, etc. The loss of connectivity issues may be identified whenthere is no communication from one end of a virtual circuit to anotherend of the virtual circuit. The issue may be caused by configurationerrors, or it may be caused by physical failures. Ping test of thevirtual circuit end points or intermediate points may be performedisolate the cause of the issue. The performance issues may be related toloss of frames, slow or delay delivery of frames, delay variance (orjitter), or service throughput. Other issues may be related to queuing,drops of frames, etc.

Marketplace for Potential Partners

FIG. 6 is a block diagram that illustrates an example of a marketplace,in accordance with some embodiments. In addition to the switch fabricplatform, the combination of the services offered by the web portal 200and the Ethernet exchanger 100 offers access to a unique and richecosystem of potential content and technical partners in a securecollocation facility. The Ethernet exchanger 100 is integrated with theweb portal 200 to form a marketplace where the carriers can learnservices offered by other carriers, qualify them and set up connectionswith the other carriers, the web portal 200 including a configurationmodule 650 to allow the carriers to publish information, findinformation published by other carriers, and fill out templates based oninformation provided by the carriers. The web portal 200 is configuredto cause the Ethernet exchanger 100 to provision the virtual circuitsbased on the filled out templates.

The marketplace 600 allows the discovery and sale of network servicesamong the carriers within the secure collocation facility. This enablesthe carriers 1 to “n” to seamlessly extend their global reach and depth.The market for the many-to-many E-NNIs is driven by the needs ofcarriers to extend their Ethernet services beyond the physical footprintor capabilities of their asset or infrastructure. The marketplace 600 isdesigned to bring carriers together and interconnect their networksregardless of the platforms (e.g., Ethernet, MPLS, SASS, etc). Using themarketplace 600, the carriers can search and review services offered byother carriers, selectively identify services that meet theirrequirements and negotiate purchases with the desired carriers. FIG. 9illustrates an overall example diagram of a representation of amarketplace that includes a web portal and an ExternalNetwork-to-Network Interface (E-NNI), in accordance with some exampleembodiments. The example illustrates the integration of the web portaland its functionalities, the ENNI infrastructure and itsfunctionalities, the roles of the representatives of the carriers, andtype of data generated based on the interactions between therepresentatives of the carriers and the portal infrastructure as well asthe ENNI infrastructure, along with other relevant information.

Flow Diagrams

FIG. 7A is an example flow diagram that illustrates a process ofproviding interconnectivity services to the carriers, in accordance withsome embodiments. At block 705, requests to become participants may bereceived from a plurality of carriers. The requests may be received viathe web portal 200. At block 710, each carrier is qualified andassociated with a port of the Ethernet exchanger 100. At block 715,information about the networks of the carriers is received. Theinformation may be received via the web portal 200 and its webtemplates. It may be noted that the operations described in blocks 710and 715 may be interchanged depending on the implementation.

At block 720, the services that the carriers want to showcase to othercarriers may become accessible in a marketplace. The marketplace mayalso provide mechanism to enable the carriers who have networkrequirements to post them. As mentioned above, for some embodiments,this posting of the requirements may be in the form of an RFQ, and theRFQ may be sent to the appropriate carriers who offer network servicesthat match with the requirements. The marketplace also provides eachcarrier to have a storefront so that their network services can bedisplayed, searched, viewed and ordered by other carriers.

Based on the carriers becoming partners, they may generate requests tohave the connections established, as shown in block 725. At block 730,the Ethernet exchanger 100 provisions the virtual circuits to connectthe networks of the requesting carriers. At block 735, the virtualcircuits are monitored for potential issues and appropriate statusinformation is provided to the carriers.

FIG. 7B is an example flow diagram that illustrates a process of reusingexisting carrier's information to establish multiple virtual circuits,in accordance with some embodiments. At block 750, a request is receivedto establish a virtual circuit between a first carrier and a secondcarrier. At block 755, information about the first carrier and thesecond carrier is retrieved from a database. The information wasprovided by the first and second carriers as part of them becoming aparticipant. At block 760, a first virtual circuit is provisioned.

At block 765, another request is received to establish a virtual circuitbetween the first carrier and a third carrier. At block 770, informationabout the first carrier and the third carrier is retrieved from thedatabase. It is noted that there is no need for the first carrier toprovide the same information again for this request. The sameinformation stored in the database for the first carrier is reused. Theinformation about the third carrier was also provided when it became aparticipant. At block 775, a second virtual circuit is provisioned.

FIG. 7C is an example flow diagram that illustrates a process offacilitating partnership among the carriers, in accordance with someembodiments. At block 780, a web portal is provided to enable thecarriers to interact with one another. The web portal is associated withan E-NNI infrastructure that includes a switch fabric and one or moreEthernet exchangers. The web portal includes options to enable a firstcarrier to submit a quote request (or RFQ) for network services to asecond carrier. Both the first and the second carrier have alreadyregistered and become participants of the services offered by the webportal and the underlying E-NNI infrastructure. At block 785, the quoterequest is received from the first carrier. At block 790, the quoterequest is sent to the second carrier. The second carrier may review thequote request, provide a solution, and come to terms with the firstcarrier independent of the web portal.

At block 795, a request to establish a virtual circuit between the firstand the second carriers is received. At block 798, the provisioning andconfiguration of the virtual circuit is performed based on theinformation stored for the first and the second carriers and based onany additional information provided with the request.

System Diagram

FIG. 8 illustrates an example diagram of a representation of a machinein the example form of a computer system that may be used, in accordancewith some example embodiments. As an example, computer system 800 may bea client computer system or machine used by a carrier to access the webportal 200. As another example, the computer system 800 may be acomputer system where programs associated with the web portal 200 may bestored and executed.

A set of instructions, for causing the machine to perform any one ormore of the methodologies discussed herein, may be executed. Inalternative embodiments, the machine operates as a standalone device ormay be connected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in server-client network environment, or as a peermachine in a peer-to-peer (or distributed) network environment. Themachine may be a server computer, a client computer, a personal computer(PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant(PDA), a cellular telephone, a web appliance, a network router, switchor bridge, or any machine capable of executing a set of instructions(sequential or otherwise) that specify actions to be taken by thatmachine. Further, while a single machine is illustrated, the term“machine” shall also be taken to include any collection of machines thatindividually or jointly execute a set (or multiple sets) of instructionsto perform any one or more of the methodologies discussed herein.

In the current example, computer system 800 may include a processor 802(e.g., a central processing unit (CPU), a graphics processing unit(GPU), or both), a main memory 804 and a static memory 806, whichcommunicate with each other via a bus 808. The computer system 800 mayfurther include a video display unit 810 (e.g., liquid crystals display(LCD) or a cathode ray tube (CRT)). The computer system 800 alsoincludes an input device 812 (e.g., a keyboard), a cursor control device814 (e.g., a mouse), a disk drive unit 816, a signal generation device818 (e.g., a speaker) and a network interface device 820.

The disk drive unit 816 includes a machine-readable medium 822 on whichis stored one or more sets of instructions (e.g., software 624)embodying any one or more of the methodologies or functions describedherein. The instructions 824 may also reside, completely or at leastpartially, within the main memory 804, the static memory 806, and/orwithin the processor 802 during execution thereof by the computer system800. The main memory 804 and the processor 802 also may constitutemachine-readable media.

The instructions 824 may further be transmitted or received over anetwork 826 via the network interface device 820. Applications that mayinclude the apparatus and systems of various embodiments broadly includea variety of electronic and computer systems. Some embodiments implementfunctions in two or more specific interconnected hardware modules ordevices with related control and data signals communicated between andthrough the modules, or as portions of an application-specificintegrated circuit. Thus, the example system is applicable to software,firmware, and hardware implementations.

In example embodiments, a computer system (e.g., a standalone, client orserver computer system) configured by an application may constitute a“module” that is configured and operates to perform certain operationsas described herein below. In other embodiments, the “module” may beimplemented mechanically or electronically. For example, a module maycomprise dedicated circuitry or logic that is permanently configured(e.g., within a special-purpose processor) to perform certainoperations. A module may also comprise programmable logic or circuitry(e.g., as encompassed within a general-purpose processor or otherprogrammable processor) that is temporarily configured by software toperform certain operations. It will be appreciated that the decision toimplement a module mechanically, in the dedicated and permanentlyconfigured circuitry, or in temporarily configured circuitry (e.g.configured by software) may be driven by cost and time considerations.Accordingly, the term “module” should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired) or temporarily configured(e.g., programmed) to operate in a certain manner and/or to performcertain operations described herein.

While the machine-readable medium 822 is shown in an example embodimentto be a single medium, the term “machine-readable medium” should betaken to include a single medium or multiple media (e.g., a centralizedor distributed database, and/or associated caches and servers) thatstore the one or more sets of instructions. The term “machine-readablemedium” shall also be taken to include any medium that is capable ofstoring, encoding or carrying a set of instructions for execution by themachine and that cause the machine to perform any one or more of themethodologies of the present description. The term “machine-readablemedium” shall accordingly be taken to include, but not be limited to,solid-state memories, optical and magnetic media, and carrier wavesignals.

As noted, the software may be transmitted over a network using atransmission medium. The term “transmission medium” shall be taken toinclude any medium that is capable of storing, encoding or carryinginstructions for transmission to and execution by the machine, andincludes digital or analog communications signal or other intangiblemedium to facilitate transmission and communication of such software.

Integration of Web Portal and Switch Fabric

FIG. 9 is a block diagram that illustrates an overall examplerepresentation of a marketplace that includes a web portal, inaccordance with some example embodiments. The example illustrates portalexperience by showing interactions between the carriers and the webportal 200, the functions performed by the web portal 200, andrepresentative roles, rights and permissions. The example alsoillustrates how the carriers' information is collected and used, and theintegration of the web portal with the portal infrastructure and theE-NNI or network infrastructure as related to auto provisioning of thevirtual circuits.

The diagram in FIG. 9 includes application layer 905, roles layer 910,function layer 915, data layer 920 and back office and network layer925. The back office and network layer 925 includes portalinfrastructure 930 and logic that performs operations relating to theweb portal. These operations may include presenting the templates andsoliciting information from the carriers, extracting the informationfrom the templates, storing the extracted information into the database,etc. It may be noted that the templates may solicit information from theparticipating carriers by different mechanisms including, for example,manual entry, selection of possible entries presented in a pull downtype menu, selection of existing information, and auto-populating fieldsof the templates. Other operations may be related to performance,security, availability, analytics, CMS, IDM, user experience, andlocalization. The portal infrastructure 930 may include logic forenterprise application integration.

The back office and network layer 925 also includes E-NNI infrastructure935 and logic that performs operations relating to the switch fabric andthe Ethernet exchanger. These operations may include provisioningvirtual circuits to interconnect private Ethernet networks of thecarriers, translating the Ethernet frames, mapping QoS, monitoring andtroubleshooting network issues using NMS and OSS, generating supporttickets, servicing APIs, etc. The E-NNI infrastructure 935 may includelogic for switch fabric integration. The operations associated with theportal infrastructure 930 and the E-NNI infrastructure 935 may beimplemented in software, hardware, or a combination of both.

The roles layer 910 illustrates different representative's roles thatmay interact with the web portal. For some embodiments, each carrier mayassign a representative to serve as an administrator. The administratorwill need to be registered with the web portal. The administrator mayhave all the necessary rights and permissions to perform operations inthe web portal on behalf of the carrier. The administrator may inviteother members of the carrier to join as the carrier's representatives.This feature provides the carrier complete control over roles that eachcarrier's representatives may be assigned. This may be referred to asself-service administration. Using this approach, the administrator onlyneed to send out the invitation to the prospective representatives. Theadministrator does not have to deal with their credentials like settingup user ID and passwords, etc. It is up to the new representatives tocreate their own profiles, credentials, passwords, security questions,and so on. None of that information is ever passed to the administrator,which is a huge convenience for setting up new representatives. The riskof passwords and credentials being exposed to others is minimized. Itmay be noted that the invitation of the prospective representatives andthe setting up of their profiles and credential information do not relyon any interaction with the service provider of the web portal. For someembodiments, functions of the administrator may optionally be performedby the service provider of the web portal. One example of a serviceprovider of the web portal is Equinix, Inc. headquartered in FosterCity, Calif.

The administrator feature is very convenient because the carriers candecide which roles and responsibilities they want to give to their groupof representatives. The carriers can restrict representatives based ontheir roles and limit them to only duties that the carriers want them toperform. For example, only an administrator can submit a service requestfor a virtual circuit or a change request for virtual circuit. Asanother example, a representative in the sales role cannot have accessto the monitoring and troubleshooting information. For some embodiments,the administrator can invite employees of the same carrier as well asnon-employees to become representatives of the carrier. For example, thenon-employees may be third party contractors who act on the carrier'sbehalf and under some type of agreement with the carrier. In addition toinviting new representatives, the administrator may also perform otheradministrative operations including, for example, create/terminateusers, modify users, assign roles, rights and permissions, resetpassword, etc.

For some embodiments, when a new representative registers with the webportal and create necessary credentials, that new representative mayinitially have no permission rights to perform any operations, untilauthorization is given by the administrator. For example, theadministrator may review the profile of the new representative and grantthe new representative certain access rights. This may be in the form ofcheck boxes. The access rights are then appended to the profile of thenew representative and that becomes the new representative personalizedexperience on the web portal. For some embodiments, the web pages thatare presented to a representative are personalized for thatrepresentative based on the granted access rights. This allows eachrepresentative to have a unique and personalized experience wheninteracting with the web portal. The representatives in the differentroles may still enjoy personalized experience with the web portal eventhough they may not be performing the same operations.

In the diagram of FIG. 9, the roles layer 910 illustrates the followingroles: administrator, product manager, sales (as related to litbuildings), carrier management, bid team, sales (as related to quotes),procurement, provisioning, engineering, and NOC. A representative in theproduct manager role is allowed to complete qualification form, viewinformation of other participants, view other participants'qualification, restrict qualification view, etc. For example, a productmanager for a carrier may not want representatives of a competingcarrier to view the qualification information of the carrier that theproduct manager works for. A representative in the sales lit buildingrole is allowed to update the lit building list (LBL), update the LBL,view the LBL online, export the LBL, restrict access to the LBL, etc. Arepresentative in the carrier management role and/or in the bid teamrole is allowed to submit RFQ, view open RFQ, notify open RFQ, exportRFQ, etc. A representative in the sales quote role is allowed to submitquote, save in-process quote, queue quote, export quote, notify quote,etc. A representative in the procurement role is allowed to order crossconnect, order virtual cross connect, view open orders, notify orderconfirmation, view order history, etc. A representative in theprovisioning role is allowed to notify, view, queue and approve pendingorder, auto provision approved orders, notify activation/verification,etc. A representative in the engineering role and/or NOC role is allowedto view NOC contacts, view escalation process, remedy integration, viewservice link stats, view monitoring history, etc.

The application layer 905 includes web services that are extended to thecarriers via APIs to enable the carriers' applications to communicatedirectly with the web portal. The APIs may tell the carriers how to sendthe information and how the information is received by the web portal.The API may include information that enables the carriers' applicationto do the handshaking, mapping, and conversion between the differentprotocols and applications over to the standard used by the switchfabric. This may be convenient for the carriers that want to transmit alot of information and would prefer, for example, batch processing overbulk processing. One example is an API that allows the carriers to pushthe lit building list (LBL). An LBL contains the buildings that arewired for Ethernet services and the characteristics of those Ethernetservices. The carriers may use tools and various applications tomaintain an LBL. The carrier may work with and maintain this list ontheir systems. However, the LBL API allows the lit building listinformation in the carriers' database to be pushed across the API andreplicated onto the switch fabric's database without any manual dataentry. The API is coded to receive the data in the proprietary formatand convert the information into the standard format used in the switchfabric's database, and is also coded to automatically facilitate pushingof data from the carriers' database onto the switch fabric's databasewithout any manual data entry.

Another example is an API that allows the carriers to push the carriers'pricing information. The quoting and pricing API enables the carriers touse their proprietary tools and various applications to generate,maintain, and track quoting and pricing information while that same datais replicated over the API into the ENNI's database. Yet another exampleis an API that allows pulling/pushing troubleshooting and ticketinginformation from the web portal and the switch fabric. One example of aticketing system used by the switch fabric is the Remedy system by BMCSoftware, Inc of Houston, Tex. Remedy is a customer relationship toolwhich can be used to log/monitor the issues or problems faced by thecarriers by the means of incident management tickets. Each ticketrepresents an issue assigned to a support team to resolve.

The function layers 915 include functions that correspond to theoperations performed by each of the roles in the roles layer 910. Thesefunctions include administration, qualification, list, RFQ, quote,purchase, receive, inventory and provision, and monitor andtroubleshoot. The data layer 920 includes data that may be generated bythe functions of the functions layer 915. The data may include userroles, rights and permission, participant listings and qualificationrecords, LBL, open RFQs and directed RFQs, bids and quotes, orders,confirmation, activations and reports. It may be noted that by allowingthe carriers to provide their LBL, the process of identifying a litbuilding becomes much faster and easier. The LBL of all theparticipating carriers can be stored in a searchable and relationaldatabase so that they can be discovered by, for example, street address,metropolitan areas, cities, zip codes or other similar generalgeographical identifying conveyed information. Being able to discoverthe LBL and being to place an order via a web portal that is integratedwith a switch fabric enable the carriers to be able to connect and takeadvantage of the services of other carriers almost immediately.

For some embodiments, a the Ethernet switch platform may include abilling support system (BSS) to enable ordering, billing, keeping trackof carriers, and managing carrier relationship. For some otherembodiments, the Ethernet switch platform may include a service bureausystem to enable the carriers to use the web portal to negotiate andenter into agreements for network services. For example, the carrierscan use the web portal to publish and search for network services, tonegotiate and become partners, to place provisioning orders, and tomonitor and diagnose network issues, and to pay for services received.

FIG. 10 illustrates an example screen of a web portal, in accordancewith some example embodiments. Screen 1000 may be associated with a homepage of the web portal. It may include options to enable the carriersand their representatives to perform operations as described in FIG. 9.The web portal (or web-enabled user interface) may be resident on aserver and is configured to present web pages including the home pageand templates to a browser application on a client machine to solicitinformation from the participating carriers. The information is thenextracted from the web pages and the templates and stored in anassociated database. This enables the participating carriers to publishnetwork services and capabilities offered, search for network servicesand capabilities offered by each carrier, submit requests for quotes(RFQs) and responses to the RFQs, initiate a provisioning of the virtualcircuits between their private Ethernet networks, and monitor andtroubleshoot the virtual circuits as well as their own private Ethernetnetworks from the web portal. This provides the carriers end-to-end(e.g., network 1, virtual circuit, network 2) monitoring andtroubleshooting capabilities.

Referring to the screen 1000, Partners option 1004 may allow viewing ofparticipating carriers' information. This may include a company profile,qualification information, LBL information, etc. Buy option 1006 mayallow the representatives to submit RFQs, view open RFQs, export RFQs,etc. Sell option 1008 may allow the representatives to update LBL,submit quotes, etc. Order option 1010 may allow the representatives torequest for provisioning of virtual circuits. Monitor option 1012 mayallow the representatives to receive status and diagnostic informationfrom the integrated switch fabric. Profile option 1014 may allow therepresentatives to review and update their profiles. User managementoption 1016 may allow the administrator representatives to performoperations as described above with FIG. 9. It may be noted that,depending on the role of a representative from a carrier, some of theoptions described may not be visible. For example, when a representativeassigned with the NOC role signing on to the web portal, thatrepresentative may not see the order option 1010. Being able to view theorder option 1010 is the experience that may be reserved for therepresentatives who are assigned the procurement or provisioning roles.

For some embodiments, the web portal may include a screen that providesa search option to allow the representatives to search for informationrelated to the lit buildings. For example, the screen 1000 includes asearch box 1020 that includes an input area 1022 to specify an addressand an input area 1024 to specify a name of a metropolitan area or acity. Optionally, the search box 1020 may include input areas to allowentry of a zip code or other similar general geographical identifyingconveyed information to enable searching for the list buildings based onthese search parameters. For example, instead of using a street address,the input area 1022 may be used for a zip code. After an address and/ora name of a metropolitan area or city are specified, button 1025 may beused to initiate the search of the database. The screen 1000 may alsoinclude a side bar or queue area 1026 to display other relatedinformation such as, for example, the number of new partners, the numberof new bids, the number of new RFQs, and the number of new serviceupdates. The position of the side bar area 1026 and the type ofinformation displayed in the side bar 1026 are illustrated as an exampleand may vary depending on the implementation of the screen 1000.

Web Portal Flow Diagram

FIG. 11 is an example flow diagram that illustrates a process ofenabling a carrier to utilize services offered by a web portal, inaccordance with some embodiments. At block 1105, the carriers go throughthe qualification process and become partners. The qualification processmay require the carriers to fill out a qualification template. At block1110, the carriers may need to provide information about their networksand services. After the carriers become participants, they may viewother carriers' services to search for services that they may need. Oncea service is identified, a carrier may submit an RFQ, as shown in block1112. At block 1114, a carrier that is offering services may receive anRFQ from another carrier. In that case, the carrier may respond to theRFQ. Based on an agreement being established between a carrier thatsubmits an RFQ and a carrier that responds to the RFQ, a purchase of theservice may occur, as shown in block 1116. At block 1118, an order maybe generated to provision a virtual circuit. At block 1120, options maybe made available to enable monitoring and troubleshooting the virtualcircuits.

Translation Flow Diagram

FIG. 12 is an example flow diagram that illustrates a process oftranslating and mapping frames for the private Ethernet networks, inaccordance with some embodiments. The Ethernet exchanger that performsthe provisioning of the circuits may be situated in a central area wherethe wirings and/or cables of the participating carriers or serviceproviders are connected to. One such central area is a data center or aco-location center. The services providers in this example flow diagramhave already been qualified and have already provided information aboutthemselves and their network services. For a virtual circuit to beestablished on their behalf, the service providers have become partnersthough a sell and buy process using, for example, RFQ.

At block 1205, a virtual circuit is established to interconnect aprivate Ethernet network of a first service provider to a privateEthernet network of a second service provider. At block 1210, based onreceiving a frame from the first private Ethernet network, the Ethernetexchanger is configured to perform handshaking, mapping, and conversionbetween different protocols and guarantee of service metrics used by thefirst and second service providers. At block 1215, the Ether exchangeris configured to perform MTU adaptation, VLAN ID and TPID translation,while preserving the PDU portion of the frame. At block 1220, thetranslated frame is transmitted onto the second private Ethernetnetwork. As noted above, the Ethernet exchanger may enable a serviceprovider to support user/clients in different geographical areas suchas, for example, in a different continent. At block 1225, the Ethernetexchanger may transmit the frame to a third private Ethernet networklocated in a different geographical area from the first private Ethernetnetwork. The first and the third private Ethernet network may be ownedand operated by the first service provider. Thus, instead of providingtheir own wiring to connect the first private Ethernet network with thethird private Ethernet network, the first service provider takeadvantages of the existing wirings of the second service providers toachieve that connection via the Ethernet exchanger.

Some portions of the detailed descriptions above are presented in termsof algorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of steps leading to a desiredresult. The steps are those requiring physical manipulations of physicalquantities. Usually, though not necessarily, these quantities take theform of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. It hasproven convenient at times, principally for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like. These algorithms may be written in a numberof different software programming languages such as C, C+, or othersimilar languages. Also, an algorithm may be implemented with lines ofcode in software, configured logic gates in software, or a combinationof both. In an embodiment, the logic consists of electronic circuitsthat follow the rules of Boolean Logic, software that contain patternsof instructions, or any combination of both.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the above discussions, itis appreciated that throughout the description, discussions utilizingterms such as “processing” or “computing” or “calculating” or“determining” or “displaying” or the like, refer to the action andprocesses of a computer system, or similar electronic computing device,that manipulates and transforms data represented as physical(electronic) quantities within the computer system's registers andmemories into other data similarly represented as physical quantitieswithin the computer system memories or registers, or other suchinformation storage, transmission or display devices.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Otherembodiments may be utilized and derived there from, such that structuraland logical substitutions and changes may be made without departing fromthe scope of this disclosure.

Thus, what has been described is an Ethernet exchanger that serves as acentral connection point to enable Ethernet service providers orcarriers to connect to one another using network-to-network interface(NNI). A web portal is integrated with the Ethernet exchanger andconfigured to enable the service providers to provide their informationand to interact with other service providers who all have wirings thatare connected to the Ethernet exchanger. The combination of the Ethernetexchanger and the web portal enables the service providers to costeffectively deliver Ethernet services to their clients in a timelymanner.

It may be appreciated that FIGS. 1-12 are merely representational andmay not be drawn to scale. Certain proportions thereof may beexaggerated, while others may be minimized. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense.

What is claimed is:
 1. An apparatus comprising: a carrier-neutralEthernet exchanger coupled to two or more private Ethernet networks ofparticipating carriers to enable the two or more private Ethernetnetworks to be interconnected at a common point, the two or more privateEthernet networks including a first private Ethernet network associatedwith a first Ethernet frame type and a second private Ethernet networkassociated with a second Ethernet frame type, wherein frames from thefirst private Ethernet network are received, translated and transmittedby the Ethernet exchanger to the second private Ethernet network,wherein frame translation performed by the Ethernet exchanger is basedon a first profile associated with the first private Ethernet networkand a second profile associated with the second private Ethernetnetwork, the first profile and the second profile stored in a relationaldatabase associated with the Ethernet exchanger, the first profile andthe second profile established based on information received from afirst participating carrier associated with the first Ethernet networkand from a second participating carrier associated with the secondEthernet network respectively using an online web portal which is hostedon a server cooperating with the Ethernet exchanger.
 2. The apparatus ofclaim 1, wherein the carrier-neutral Ethernet exchanger is configuredfor the participating carriers to connect to each other's Ethernetnetworks, with a standard network-to-network interface (NNI) and with aprocess that reuses already entered or known data preventing the processfrom having to be done from scratch each time repeatedly, wherein aconfiguration module uses templates from the online web portal tosolicit information from the participating carrier and thenautomatically extracts that information into a relational database forthe information to be reused, wherein each time a new template ispresented to the participating carrier the information now stored in therelational database is used to pre-populate known information in a newtemplate presented to the participating carrier, which allows for afaster building of the NNI process for each participating carrier in aone-to-many solution based on usage of standards and usage of knowninformation, wherein the online web portal is configured to standardizethe NNI connections via having coded routines for: a) for serviceconnectivity and fabric provisioning between carriers connected to portsof the Ethernet exchanger; b) service VLAN ID translation between thesolicited VLAN IDs of the networks creating a within multiple networkenvironments; c) service VLAN frame translation between the solicitedVLAN frame type used in each network being provisioned; d) service MTUadaptation between the solicited MTU allowed in each network beingprovisioned; and e) service VLAN TPID translation the solicited VLANTPID assigned in each network being provisioned; and any Quality ofService (QoS) parameters used in each network being provisioned
 3. Theapparatus of claim 1, wherein the Ethernet exchanger is configured toperform the frame translation of the frames received from the firstprivate Ethernet network while preserving a protocol data unit (PDU)portion of each frame, wherein the frame translation performed by theEthernet exchanger comprises translating the first Ethernet frame typeto the second Ethernet frame type.
 4. The apparatus of claim 3, whereinthe frame translation performed by the Ethernet exchanger comprisestranslating a first service type associated with the first privateEthernet network to a second service type associated with the secondprivate Ethernet network, and wherein the Ethernet exchanger includes aroutine configured perform handshaking, mapping, and conversion betweendifferent protocols and guarantee of service metrics used by the firstand second participating carriers.
 5. The apparatus of claim 1, whereinthe first profile and the second profile comprise information associatedthe first participating carrier and the second participating carrier andmade available to other participating carriers through the online webportal.
 6. The apparatus of claim 1, wherein an interconnection betweenthe first private Ethernet network and the second private Ethernetnetwork is to enable the second participating carrier to use a thirdprivate Ethernet network associated with the first participating carrierwithout the second participating carrier having a direct connectionbetween the second private Ethernet network and the third privateEthernet network.
 7. The apparatus of claim 1, wherein the Ethernetexchanger a) is configured to aggregate and translate private Ethernetservices, via templates supplied to a browser of a client machine fromthe online web portal integrated with the Ethernet exchanger, b) has aprovisioning routine to provision virtual circuits among the privateEthernet networks on behalf of the carriers, and c) is configured tofacilitate Ethernet services across multiple geographically distinctlocations.
 8. The apparatus of claim 7, wherein the Ethernet exchangeris configured to provide a many-to-many layer 2 Network-to-NetworkInterface (NNI) to enable the carriers to connect to the Ethernetexchanger and be interconnected with other carriers also connected tothe Ethernet exchanger, wherein translation of private Ethernet servicesin between the first private Ethernet network and the second privateEthernet network are performed independent of proprietary protocol usedin either private Ethernet network.
 9. The apparatus of claim 8, whereinthe Ethernet exchanger is configured to provide mechanisms to enable theparticipating carriers to monitor and troubleshoot their respectiveinterconnected private Ethernet networks end-to-end, the mechanismsincluding the online portal and one or more application programminginterfaces (APIs).
 10. The apparatus of claim 9, wherein the Ethernetexchanger is configured to enable the first private Ethernet network tobe interconnected to private Ethernet networks of two or more otherparticipating carriers simultaneously and to enable the firstparticipating carrier to take advantage of already laid-out networkwirings of the two or more other participating carriers, and wherein themultiple geographically distinct locations includes locations indifferent continents.
 11. The apparatus of claim 1, wherein the firstprivate Ethernet network of the first participating carrier can beinterconnected to the private Ethernet networks of one or more otherparticipating carriers without leaving framework of the first privateEthernet network.
 12. The apparatus of claim 1, wherein the online webportal is resident on a server and configured to present web pages andtemplates to a browser application on a client machine to solicitinformation from the participating carriers, the templates enabling thecarriers to create profile information and provide information abouttheir private Ethernet networks, wherein the information provided by thecarriers is extracted automatically from the templates via a firstextraction routine, which then stores the information in a relationaldatabase associated with the Ethernet exchanger.
 13. The apparatus ofclaim 12, wherein the Ethernet exchanger includes a configuration moduleconfigured to qualify the participating carriers, enable theparticipating carriers to search for other participating carriers andtheir services, buy and sell services to the other participatingcarriers, monitor and trouble shoot their circuits and private Ethernetnetworks end-to-end, and provide bandwidth translation and quality ofservice (Qos) mapping.
 14. The apparatus of claim 13, wherein requestfor quote (RFQ) is used to enable buy and sell services, and wherein theEthernet exchanger provisions the circuits based on the informationprovided by the participating carriers via the templates and based oninformation included in the RFQ.
 15. The apparatus of claim 14, whereinthe Ethernet exchanger includes a provisioning module configured to takethe information from the RFQ and the relational database andautomatically populate fields of a provisioning request, and whereinlogical and physical connections are established in the Ethernetexchanger based on the fields of the provisioning request tointerconnect private Ethernet networks of participating carriersinvolved in the RFQ.
 16. The apparatus of claim 1, wherein frametranslation performed by the Ethernet comprises preserving a portion ofan incoming frame including a service frame carrying data, andtranslating a portion of the incoming frame including at least MaximumTransmission Unit (MTU) translation, virtual local area networkidentifier (VLAN ID) translation and tag protocol identifier (TPID)translation.
 17. The apparatus of claim 16, wherein the Ethernetexchanger is configured to generate support ticket information andmaking the support ticket information accessible via an applicationprogramming interface (API) to enable network operation center (NOC) ofthe participating carriers to trouble shoot the circuits.
 18. A methodfor interconnecting private Ethernet networks using an Ethernetexchanger, the method comprising: establishing a virtual circuit tointerconnect a first private Ethernet network with a second privateEthernet network based on information received from a respective firstservice provider and second service provider, wherein the information isreceived via a web portal through one or more templates, the virtualcircuit established in the Ethernet exchanger coupled with the webportal which is hosted on a server and accessible via web browser on aclient machine; translating a frame received from the first privateEthernet network based on information associated with the second privateEthernet network to form a translated frame, wherein the translatingcomprises virtual local area network identifier (VLAN ID) translation,tag protocol identifier (TPID) translation, and frame type translation,and wherein the translating is performed while preserving a protocoldata unit (PDU) portion of the frame; and transmitting the translatedframe to the second private Ethernet network via the virtual circuit.19. The method of claim 18, further comprising: performing maximumtransmission unit (MTU) adaptation on the frame; and performingnecessary handshaking, mapping, and conversion operations betweendifferent protocols associated with the first private Ethernet networkand the second private Ethernet network, wherein the translated frame istransmitted to a destination located in a different geographical area ascompared to a location of the first private Ethernet network.
 20. Asystem comprising: means for enabling a plurality of Ethernet serviceproviders to become qualified and participate in an Ethernet switchplatform configured to provide a many-to-many layer 2 Network-to-NetworkInterface (NNI) to enable the Ethernet service providers to connect tothe Ethernet switch platform and be interconnected with other Ethernetservice providers also connected to the Ethernet switch platform; meansfor translating frames received from a first Ethernet network of a firstEthernet service provider into frames to be transmitted to a secondEthernet network of a second Ethernet service provider, wherein saidtranslating the frames includes virtual local area network identifier(VLAN ID) translation, tag protocol identifier (TPID) translation, andframe type translation, and wherein said translating is to be performedwhile preserving a protocol data unit (PDU) portion of the frames; andmeans for transmitting translated frames to the second Ethernet networkvia a virtual circuit in the Ethernet switch platform, the virtualcircuit interconnecting the first Ethernet network with the secondEthernet network via a port of the first Ethernet service provider and aport of the second Ethernet service provider.